Found 312 results for "docs fields search"

The search executed in 0.001481917 seconds. That's fast.

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / documents-list-sort-fields

documents-list-sort-fields [ { "evaluator": "document-is-folder", "condition": true, "config": { "documents-list-sort-fields": [ { "key": "title", "title": "Title", "field": "title" }, { "key": "description", "title": "Description", "field": "description" }, { "key": "createdOn", "title": "Created On", "field": "_system.created_on.ms" },

Score: 5.5791883

Gitana / 4.0 / Developers / User Interface Customization / Contexts / documents-list-sort-fields

documents-list-sort-fields [ { "evaluator": "document-is-folder", "condition": true, "config": { "documents-list-sort-fields": [ { "key": "title", "title": "Title", "field": "title" }, { "key": "description", "title": "Description", "field": "description" }, { "key": "createdOn", "title": "Created On", "field": "_system.created_on.ms" },

Score: 5.5791883

Gitana / 3.2 / Guide / Guide / Content Modeling / Relator Properties

Relator Properties Cloud CMS provides support for properties that auto-manage their relationships between multiple nodes in the content graph. Whenever you intend to connect two nodes together, it is often convenient to model a property on one or both of the nodes involved in the relationship such that the properties maintain information locally on the endpoints about the relationship. Such properties are known as "relator properties". Consider a Store that sells Books. Books are written by Auth

Score: 5.549176

How to get a content definition JSON from the Cloud CMS API?

There are a couple of ways to do this. The first is simply use the node GET call and pass in the qname like this: GET /repositories/{repositoryId}/branches/{branchId}/nodes/{qname} http://api.cloudcms.com/docs#!/node/get_repositories_repositoryId_branches_branchId_nodes_nodeId This will give you back the JSON for the definition. Another way is to use this variation: GET /repositories/{repositoryId}/branches/{branchId}/definitions/{qname} http://api.cloudcms.com/docs#!/branch/get_repositories_rep

Score: 5.0940137

How to limit the fields that come back in a query

Query API calls like http://api.cloudcms.com/docs#!/node/post_repositories_repositoryId_branches_branchId_nodes_query support a parameter named _fields which defines an object specifying the node properties you want to include in the result set for matching nodes. For example in the following query I want the title, subTitle and slug fields returned: { "_type":"my:article", "_fields":{ "title":1, "subTitle":1, "slug":1 } } The result set would look something like the

Score: 4.56062

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / project-search-list-selected-actions

project-search-list-selected-actions [ { "config": { "project-search-list-selected-actions": [ { "action": "deploy-nodes", "allowPermission": [ "deploy", "undeploy" ], "order": 10000 } ] } }, { "config": { "project-search-list-selected-actions": [ { "action": "delete_documents", "order": 5, "allowPermission": [ "delete" ]

Score: 4.551641

Gitana / 4.0 / Developers / User Interface Customization / Contexts / project-search-list-selected-actions

project-search-list-selected-actions [ { "config": { "project-search-list-selected-actions": [ { "action": "deploy-nodes", "allowPermission": [ "deploy", "undeploy" ], "order": 10000 } ] } }, { "config": { "project-search-list-selected-actions": [ { "action": "delete_documents", "order": 5, "allowPermission": [ "delete" ]

Score: 4.551641

Is there a programmatic way to add more content to workflows?

There is a programmatic way to add more content to workflows once they're in-flight. However, once the workflow is in-flight, the workflow process instance isn't the correct place to add things. Instead, you'd want to add new content to a workflow task. Essentially, a workflow is made up of a series of tasks. When the workflow transitions from one node to another in the workflow model, it instantiates a new task and the task holds the state (and references to documents) for that phase of the wor

Score: 3.4653955

Using the JavaScript driver to run an elasticsearch query

The Cloud CMS REST API allows for elasticsearch queries against a branch. The API endpoint is POST /repositories/{repositoryId}/branches/{branchId}/nodes/search The payload is a JSON object containing a top-level property called "search" which wraps the elasticsearch DSL query. The JavaScript driver exposes this call on the Branch object using the searchNodes() methods. Examples: 1) Search for nodes containing the keyword "hello" in any property: req.branch(function (err, branch) { branch.trap(f

Score: 3.3970652

How to Retrieve content by their document library path

You can retrieve content by their document library path using the CMS API using the Node API. For example, you can paginate through the children of a node using this call: http://api.cloudcms.com/docs#!/node/get_repositories_repositoryId_branches_branchId_nodes_nodeId_children GET /repositories/{repositoryId}/branches/{branchId}/nodes/{nodeId}/children?path={path} In this case, you would set "nodeId" to the value "root" to indicate the root node. And then use "path" to describe the offset. If yo

Score: 3.0693564

Gitana / 4.0 / Forms / Fields / Overview

Fields Further Reading Address Field Any Field Array Field Checkbox Field Chooser Field CKEditor Field Color Field Color Picker Field Country Field Currency Field Date Field Date Time Field Editor Field Email Field File Field Grid Field Hidden Field Image Field Integer Field IPv4 Field JSON Field Lower Case Field Map Field Markdown Editor Field Number Field Object Field Option Tree Field Password Field Personal Name Field Phone Field Pick A Color Field Radio Field Search Field Select Field State

Score: 3.025279

What is the reason for "Failed to index node"?

If you scan your log entries and see "Failed to index node", this indicates that Elastic Search failed to update its index for a node. Cloud CMS tells Elastic Search to updates its index whenever a node is created or updated. When a node is deleted, Cloud CMS tells Elastic Search to remove the node from its index. This error message means that Elastic Search failed to update the index and therefore the index wasn't updated. If you open up the error, you may see further information that indicates

Score: 3.0173337

Gitana / 3.2 / Guide / Guide / User Interface / Add-ons

Add-ons Cloud CMS Add-Ons let you enhance your editorial user interface with new features and capabilities that integrate to popular third-party services like YouTube, Vimeo and Google Docs. Add-ons provision your editorial environment with things like: new form field types that integrate to third-party services new user interface pages for browsing and working with media from third-party services new actions or rules to enhance your repository's business logic new content types, associations an

Score: 2.7619333

Gitana / 4.0 / User Interface / Add-ons / Overview

Add-ons Cloud CMS Add-Ons let you enhance your editorial user interface with new features and capabilities that integrate to popular third-party services like YouTube, Vimeo and Google Docs. Add-ons provision your editorial environment with things like: new form field types that integrate to third-party services new user interface pages for browsing and working with media from third-party services new actions or rules to enhance your repository's business logic new content types, associations an

Score: 2.7619333

Gitana / 3.2 / Guide / Guide / Reports

Reports All of the objects that you place into Cloud CMS can be operated against to produce exports that consist of consolidated or reported information. You can use this capability to generate reports in CSV (comma-separated value) format as well as merged PDFs and ZIP archives. Exports are generated from collections of objects. These objects might be collected by hand or they might consist of results sets from a document list, search page or report record set. The Cloud CMS user interface prov

Score: 2.6326838

Gitana / 4.0 / Data Engine / Nodes / Reports

Reports All of the objects that you place into Cloud CMS can be operated against to produce exports that consist of consolidated or reported information. You can use this capability to generate reports in CSV (comma-separated value) format as well as merged PDFs and ZIP archives. Exports are generated from collections of objects. These objects might be collected by hand or they might consist of results sets from a document list, search page or report record set. The Cloud CMS user interface prov

Score: 2.6326838

Gitana / 3.2 / Guide / Guide / Forms / Fields / CK Editor

CK Editor ID: ckeditor The ckeditor field renders the popular CKEditor HTML control. This offers a fully-featured HTML editor on top of a string schema type. It is ideal for situations where you wish to provide your editorial team with the ability to edit HTML visually and offers a large range of plugins and behaviors that you can customize. For basic information of what is possible in terms of configuring this field type, please view the Alpaca Forms documentation for the CKEditor field. Config

Score: 2.585127

Gitana / 4.0 / Forms / CMS / Fields / CK Editor

CK Editor ID: ckeditor The ckeditor field renders the popular CKEditor HTML control. This offers a fully-featured HTML editor on top of a string schema type. It is ideal for situations where you wish to provide your editorial team with the ability to edit HTML visually and offers a large range of plugins and behaviors that you can customize. For basic information of what is possible in terms of configuring this field type, please view the Alpaca Forms documentation for the CKEditor field. Config

Score: 2.585127

Gitana / 4.0 / Forms / Fields / Date Field

Date Field The date field. The Date Field uses the Bootstrap Datetime picker under the hood. You can learn more about the picker at it's GitHub project page: https://github.com/Eonasdan/bootstrap-datetimepicker. For more information on date and time formatting strings, see the Moment.js documentation: http://momentjs.com/docs/. With this control, you can pass any of the bootstrap-datetimepicker options information through to the underlying control via the options.picker setting. Properties Title

Score: 2.5263166

REST based access calls

The authentication mechanism in Cloud CMS is OAuth 2.0. While you can use any of the flows, the easiest one to begin with is "password". We've outlined a basic example here using Advanced REST Client to show our API-first platform in action. First, from your Cloud CMS platform home page, navigate to "Manage Platform" and select the "API Keys" section to list all available projects for remote access: If you have no keys for your project then create a new "Application" from "Manage Platform" and t

Score: 2.5263166

Gitana / 3.2 / Guide / Guide / User Interface / Awareness

Awareness Awareness service allows you to see who's viewing/editing the same document with you in real-time, just like google docs. In the above screenshot, there are three user avatars showing in the top right corner. That indicates that there are three people (including yourself) viewing/editing this document right now. Hover on each avatar to see the detail -- find out whom they are if you don't recognize the avatar. Auto Lock on Document Editing There are three possible phases you might see

Score: 2.4550252

Gitana / 4.0 / User Interface / User Interface / Awareness

Awareness Awareness service allows you to see who's viewing/editing the same document with you in real-time, just like google docs. In the above screenshot, there are three user avatars showing in the top right corner. That indicates that there are three people (including yourself) viewing/editing this document right now. Hover on each avatar to see the detail -- find out whom they are if you don't recognize the avatar. Auto Lock on Document Editing There are three possible phases you might see

Score: 2.4550252

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / project-field-templates

project-field-templates [ { "evaluator": "context-project", "config": { "project-field-templates": { "templates": [ { "key": "text", "title": "Text", "type": "string/text", "description": "Text value. e.g. title, name, header", "icon": "fa fa-align-left" }, { "key": "number", "title": "Number", "type": "number/number", "description": "N

Score: 2.4414053

Gitana / 4.0 / Developers / User Interface Customization / Contexts / project-field-templates

project-field-templates [ { "evaluator": "context-project", "config": { "project-field-templates": { "templates": [ { "key": "text", "title": "Text", "type": "string/text", "description": "Text value. e.g. title, name, header", "icon": "fa fa-align-left" }, { "key": "number", "title": "Number", "type": "number/number", "description": "N

Score: 2.4414053

Gitana / 3.2 / Guide / Guide / Query

Query Cloud CMS provides SQL-like, structured query for all of your content. The platform uses MongoDB under the hood to store the JSON for your content. MongoDB offers a powerful, unmatched query engine so that you can execute complex lookups of your content to support both your editorial and runtime application needs. The platform also offers "composite" query operations which let you layer MongoDB queries on top of Elastic Search DSL searches and traversals around node objects. Cloud CMS auto

Score: 2.3577666